home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
FishMarket 1.0
/
FishMarket v1.0.iso
/
fishies
/
301-325
/
disk_313
/
uucp
/
uucp1.lzh
/
man
/
Getty
< prev
next >
Wrap
Text File
|
1989-10-27
|
6KB
|
182 lines
NAME
Getty
SYNOPSIS
Getty -Sserialname -Uunit -Bbaud -Bbaud.. -Mc
-m1 -r0 -h0 -c0 -xn -A -7 -0 [modem-cmds]
NOTE BUG: You currently cannot run more than one Getty per
*DEVICE NAME*, i.e. on more than one unit per device.
DESCRIPTION
Getty hangs on the specified serial port (serial.device unit 0 by
default) waiting for connections via the connected modem. Once
a connection is accepted Getty adjusts to the proper baud rate
using the CONNECT message, -B, -A options, then provides a
Login: request to the caller.
NOTE: A CONNECT message from the modem with no baud rate specified
will cause Getty to use the first baud rate in the -B list. If
the -A option is specified, Getty *always* uses the first baud
rate in the -B list and never switches to any other baud rate.
If the caller sends a line-break Getty will switch to the next
baud rate in the specified list. During the initialization phase
of the modem (before the first call and after a disconnect), Getty
readjusts the baud rate to the first specified rate.
Getty disconnects any caller who cannot provide a legal Login and
Password within 60 seconds.
Upon receiving a legal Login and and Password, verified via
GETTY:PASSWD, Getty will execute the program specified in
GETTY:PASSWD, usually UUCICO, and stay off the line until
UUCICO returns. When UUCICO returns, Getty will disconnect
the caller and reset the modem, returning to its original state.
The file GETTY:Getty-Header contains a couple lines of text
that are sent over the serial port before the Login: request.
In it you normally have your machine type, name, etc...
Getty runs the specified program in the password entry adding
the following arguments:
-Getty -DEVICE devicename -UNIT unitnumber
(uucico will recognize said arguments and not attempt to
initialize / waitfor calls / hangup the modem itself)
Getty also recognizes when other amiga programs open the
serial.device it is waiting on and will get off the line for
the duration of the other program's connect (i.e. you can run
terminal programs without having to BREAK Getty).
NOTE 1: Getty can only get off the line when it is idle,
waiting for carrier. UUCP related programs will
also use a separate locking mechanism to properly
talk to Getty under other circumstances.
NOTE 2: Getty will attempt a disconnect sequence when it
reestablishes control after the other program
closes the serial.device . Getty checks the
device count once a second.
OPTIONS
-Sserialname Specify serial device, default "serial.device"
-Uunit Specify unit number, default 0
-Bbaud Specify up to 32 baud rates
-A Specify modem will adjust to a single baud
rate (locks the serial.device at the first
baud rate in the -B list)
-7 Use SERF_7WIRE protocol while online,
else uses no protocol while online. If
you are using a modem with speed conversion
you need this option or you will most likely
overflow the modem's buffer!
-Mc Select Modem type,
c = m Multimodem
h Hays
d Dumb (no AT or +++ commands are
sent to the modem ever).
-mn Set modem speaker level, default 0.
(ATMn command)
-rn Set modem to answer on the Nth ring
(modem must support ATMn). 0 disables
answer capability. The default is to
answer on the second ring.
-h0 Ignore CD (carrier detect). If this option
is specified a continuous carrier detect is
assumed, causing Getty to request Login:'s
over the line as soon as it receives a CONNECT
message.
It is suggested you ONLY use this option
when combined with -c0
-c0 Do NOT look for a CONNECT message from the
modem... useful for dumb modems.
-d0 Normally Getty will disconnect by dropping
DTR. If this option is specified, Getty will
use the less reliable +++ ATH0 sequence.
-xn Set debugging level to n. If specified
debugging messages are sent to stdout instead
of GETTY:LOGFILE
Note: to avoid GETTY:LOGFILE getting too
large for busy systems, you can always add
an entry to your crontab to delete it once
a week (or whenever).
-0 Kill any already-running Getty for this
serial port and unit.
modem-cmds You may specify up to 16 specific commands
to be sent to the modem whenever it is
initialized (usually after a disconnect
and on startup). Each command will be
sent to the modem with a CR on the end and
a seconds delay afterwords. Example:
ATS2=.
This is useful for provided specialized
modems with the appropriate initialization
strings.
EXAMPLE
; Run a Getty for a MultiModem
run >nil: <nil: Getty -Mm -A -B19200
; Run a Getty for a Hays Modem
run >nil: <nil: Getty -Mh -B1200 -B2400
; Modify options to a Getty already running in the background
Getty -m1 ; Set speaker on during dialing
Getty -m0 ; speaker off at all times.
Getty -0 ; kill background Getty
EXAMPLE CRONTAB ENTRIES
Assuming a getty has been run in the background from your
startup sequence, the most common desire is to disable the
modem speaker while you are asleep, and enable it at other
times. The following crontab entry will accomplish this:
0 23 * * * getty -m0
0 11 * * * getty -m1
You can also kill (getty -0) or restart getty from your
crontab, though the prefered method is to leave it running
and only disable/enable the autoanswer (-r option) for those
times you wish your modem to not accept calls.
FILES/REQUIRES
GETTY:PASSWD
GETTY:Getty-Header
GETTY:LOGFILE
The NULL: handler must be mounted
The UUSER: handler must be mounted if Passwd file contains
*'d executable entries (don't confuse *'d executables
with using '*' for the password field).
REFERENCES
Getty
Passwd